Method and system for reclaiming unused resources in a networked application environment

ABSTRACT

Techniques are disclosed for reclaiming resources within a distributed computing system. A reclamation application searches the distributed computing architecture for unused resources, classifies the unused resources, and determines an expiration period based on the classification. The reclamation application determines a candidate owner of the resource based on one or more characteristics of the resource. The reclamation application then notifies the candidate owner that the resource is to be reclaimed unless claimed by the candidate owner within the expiration period. If the candidate owner claims the resource within the expiration period, then the reclamation application terminates the reclamation of the resource. If the candidate owner does not claim the resource within the expiration period, then the reclamation application reclaims the resource after the duration of the expiration period. Advantageously, this approach to reclaiming resources results in more efficient utilization of resources, lower operation and maintenance costs, and improved system security.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of the co-pending U.S. patentapplication titled, “METHOD AND SYSTEM FOR RECLAIMING UNUSED RESOURCESIN A NETWORKED APPLICATION ENVIRONMENT,” filed on May 4, 2015 and havingSer. No. 14/703,859, which is a continuation of the co-pending U.S.patent application titled, “METHOD AND SYSTEM FOR RECLAIMING UNUSEDRESOURCES IN A NETWORKED APPLICATION ENVIRONMENT,” filed on Apr. 12,2012 and having Ser. No. 13/445,877. The subject matter of these relatedapplications is hereby incorporated herein by reference.

BACKGROUND OF THE INVENTION

Field of the Invention

Embodiments of the present invention generally relate to distributedcomputing systems and methods, and more specifically to reclaimingunused resources in a networked application environment.

Description of Related Art

A broad variety of computing applications have been made available tousers over computer networks. Frequently, a networked application may beprovided using multiple interacting computing nodes within a distributedcomputing architecture. For example, a web site may be provided using aweb server (running on one node within the distributed computing system)configured to receive requests from users for web pages. The requestscan be passed to an application server (running on another node withinthe distributed computing system), which in turn processes the requestsand generate responses passed back to the web server, and ultimately tothe users.

Another example of a networked application includes a contentdistribution system used to provide access to media titles over anetwork. Typically, a content distribution system may include variousservers such as access servers and content servers. Clients may connectto the servers using a content player, such as a gaming console,computing system, computing tablet, mobile telephone, or network-awareDVD player. The content server stores files (or “streams”) available fordownload from the content server to the content player. Each stream mayprovide a digital version of various forms of video or other content,such as a movie, a television program, a sporting event, user generatedcontent, or a staged or live event captured by recorded video. Usersaccess the service by connecting to a web server, where a list ofcontent is available. Once a request for a particular title is received,the title may be streamed to the client system over a connection to anavailable content server.

One problem with distributed computing systems is that networkedapplications running on systems such as these often accumulate multipleresources, such as storage volumes and licenses for softwareapplications, some of which may have fallen into disuse. Unusedresources could be redeployed to other networked applications where theresources would be utilized more efficiently. In addition, users may payfor reserving or maintaining resources within the distributed computingarchitecture. Where resources have fallen into disuse, users may bepaying for resources that are underutilized. Further, securityvulnerabilities may arise when resources fall into disuse. Unusedresources may not receive software updates, including updates to resolvesecurity problems, and thus present a security risk to the distributedcomputing system. While unused resources may be reclaimed manually, someunused resources may be inadvertently missed due to human error, whileother unused resources may be difficult to discover using manualprocesses.

As the foregoing illustrates, what is needed is a more automated way todiscover and reclaim resources that have fallen into disuse.

SUMMARY OF THE INVENTION

One embodiment of the present invention sets forth acomputer-implemented method for reclaiming unused resources in anetworked application environment. The method includes identifying aresource that is eligible for reclaiming, determining a classificationfor the resource based on one or more classification criteria, notifyinga candidate owner of the resource that the resource is to be reclaimedat the termination of an expiration period, and if the candidate ownerclaims the resource within the expiration period, then terminating thereclamation of the resource, or if the candidate owner does not claimthe resource within the expiration period, then reclaiming the resource.

Other embodiments include, without limitation, a computer-readablemedium that includes instructions that enable a processing unit toimplement one or more aspects of the disclosed methods as well as asystem configured to implement one or more aspects of the disclosedmethods.

One advantage of the disclosed method is that unused resources in adistributed computing architecture are reclaimed and subsequently may berelinquished or redeployed, resulting in more efficient and costeffective utilization of the resources.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the manner in which the above recited features of the presentinvention can be understood in detail, a more particular description ofthe invention, briefly summarized above, may be had by reference toembodiments, some of which are illustrated in the appended drawings. Itis to be noted, however, that the appended drawings illustrate onlytypical embodiments of this invention and are therefore not to beconsidered limiting of its scope, for the invention may admit to otherequally effective embodiments.

FIG. 1 illustrates a distributed computing system configured toimplement one or more aspects of the present invention.

FIG. 2 illustrates the administration server of FIG. 1 which includesthe reclamation application, according to one embodiment of theinvention.

FIG. 3 sets forth a flow diagram of method steps for reclaiming unusedresources within a distributed computing architecture, according to oneembodiment of the present invention.

DETAILED DESCRIPTION

In the following description, numerous specific details are set forth toprovide a more thorough understanding of the present invention. However,it will be apparent to one of skill in the art that the presentinvention may be practiced without one or more of these specificdetails. In other instances, well-known features have not been describedin order to avoid obscuring the present invention. Further, particularembodiments of the invention are described using an example of anetworked application used to stream movies, music, televisionprogramming, user generated content etc., over a data communicationsnetwork to end-user client devices. However, it should be understoodthat embodiments of the invention may be adapted to discover and reclaimunused resources for a broad variety of networked applications orservices. Accordingly, references to a streaming media service aremerely illustrative and not limiting.

FIG. 1 illustrates a distributed computing system 100 configured toimplement one or more aspects of the present invention. As shown, thedistributed computing system 100 includes, without limitation, adistributed computing architecture 110 (also referred to herein as “thecloud”), a network 120, a client device 142, a communication channel130, and an administration server.

The distributed computing architecture 110 includes a plurality of“compute nodes” 102 (referred to herein as nodes). Each of the nodes 102may include a processor (CPU), a memory, a network interface controller(NIC), and one or more non-volatile storage devices such as a hard-diskdrive, a magnetic tape drive, optical disk drives, a drive array (e.g.,RAID), or the like. Each node 102 includes an operating system as wellas one or more applications stored in memory and executing on the CPU.Some of the applications may provide a software framework for variouscloud service architectures, such as a distributed database managementsystem or a distributed application system. Such applications mayexecute on a single node 102. Applications may also execute on multiplenodes 102 where portions of the application run on different nodes 102.Alternatively, multiple instances of the application, where theinstances execute on various nodes 102 within distributed computingsystem 100. The distributed computing architecture 110 provides one ormore virtual computing services via standard messaging protocols, suchas representational state transfer (REST). Examples of virtual computingservices may include processing capacity, storage, and relationaldatabases, among many other types of services. The virtual computingservices may include networked applications where various activeapplication components of the networked application execute on aplurality of nodes in communication with each other. For example, node102(0) may execute one active application component of a networkedapplication. Node 102(0) may communicate with node 102(4), where node102(4) may execute a second active application component of the samenetworked application. Node 102(4) may communicate with nodes 102(2),102(5), 102(N-1), where each of these nodes may execute an instance of athird active application component of the same networked application.The nodes 102 interconnect to each other through any technicallyfeasible means. As described below, the distributed computingarchitecture connect to external devices and other computing systems vianetwork 120 and communication channel 130.

The network 120 connects the distributed computing architecture 110 toexternal devices such as client device 142. The network 120 may includeany technically feasible networking system such as a LAN (Local AreaNetwork), a WAN (Wide Area Network), or the Internet.

The client device 142 is configured to access one or more applicationsexecuting within the distributed computing architecture 110. Forexample, the client device may access a content distribution systemexecuting within the distributed computing architecture 110 to accessmedia titles over network 120. In one embodiment, client computer 142 ismaintained by a data analyst to analyze the distributed computingarchitecture 110. The client device 142 includes a processor (CPU), amemory, a NIC, and one or more non-volatile storage devices (not shown).Similar to nodes 102, client device 142 also includes an operatingsystem as well as one or more applications, such as client application144, stored in memory and running on the CPU. The client device 142communicates with one or more of the nodes 102 via network 120 therebyallowing the client application 144 to access to or more networkedapplications executing on the distributed computing architecture 110.

The communication channel 130 connects one or more nodes 102 within thedistributed computing architecture 110 to a computing system utilizedfor configuring, maintaining, and testing the distributed computingarchitecture 110 such as the administration server 162. The network 120may include any technically feasible communication channel including apoint-to-point connection, or a networking system such as a LAN (LocalArea Network), a WAN (Wide Area Network), or the Internet.

The administration server 162 performs administrative tasks for thedistributed computing architecture 110 autonomously or in response toone or more commands issued by a system administrator. Theadministration server 162 may be any type of computing device such as apersonal computer, minicomputer or server. As shown, the administrationserver 162 may include one or more software applications that allow asystem administrator to perform various functions including, withoutlimitation, configuring, monitoring, and testing the distributedcomputing architecture 110.

In one embodiment, the administration server 162 includes a reclamationapplication 164 that enables searches for unused resources within thedistributed computing architecture 110. As described in greater detailherein, the reclamation application determines the expiration period forthe resource, identifies a candidate owner of the resource, and notifiesthe candidate owner. If the candidate owner does not claim the resourcewithin the expiration period, then the reclamation application 164 isable to reclaim the resource. The administration server 162 communicatesto one or more of the nodes 102 via communication link 130.

FIG. 2 illustrates the administration server 162 of FIG. 1 whichincludes the reclamation application 164, according to one embodiment ofthe invention. As shown, the administration server 162 includes, withoutlimitation, a central processing unit (CPU) 205, an interconnect 220, anetwork interface 215, a memory 225, and storage 230. The administrationserver 162 may also include an I/O device interface 210 connecting I/Odevices 212 (e.g., keyboard, display and mouse devices) to theadministration server 162.

The CPU 205 is included to be representative of a single CPU, multipleCPUs, a single CPU having multiple processing cores, and the like. TheCPU retrieves and executes programming instructions related to variousapplication programs residing on the administration server 162. The CPU205 is connected to other components within the administration server162 via the interconnect 220. The interconnect 220 is a communicationschannel, such as a computer bus, to provide a means of communicationamong the various components within the administration server 162. Theinterconnect 220 facilitates transmission of programming instructionsand application data between the CPU 205, network interface 215, memory225, storage 230, and I/O devices interface 210. The network interface215 provides a communication path between the administration server 162and the distributed computing infrastructure 110. The memory 225includes programming and instructions and application data for theadministration server 162. Accordingly, the CPU 205 retrieves andexecutes programming instructions stored in the memory 225. Similarly,the CPU 205 stores and retrieves application data residing in the memory225. The memory 225 is generally included to be representative of arandom access memory. The storage 230 may be any device for long termstorage of data such as a disk drive storage device. Although shown as asingle unit, the storage 230 may be a combination of fixed and/orremovable storage devices, such as fixed disc drives, floppy discdrives, tape drives, removable memory cards, optical storage, networkattached storage (NAS), or a storage area-network (SAN). The I/O deviceinterface 210 connects I/O devices 212 (e.g., keyboard, display andmouse devices) to the administration server 162.

As shown, the memory 225 includes a reclamation application 164 andstorage 230 includes a resource database 255. The reclamationapplication 164 includes a reclamation component 223 and reclamationrules 229. As noted above, the reclamation application 164 is configuredto search the distributed computing architecture 110 for unusedresources and then, if desired, reclaim the resources.

The reclamation component 223 is configured to search the distributedcomputing architecture 110 via network interface 215 to identifyresources that are eligible for reclaiming. Resources are determined tobe eligible for reclaiming based on one or more conditions including,without limitation, resources associated with out of date software,resources that have not been accessed for a pre-determined period oftime, and resources associated with a storage volume that contains nodata. When an unused resource has been identified, the reclamationcomponent 223 determines a class for the resource based on one or moreclassification criteria. For example, the reclamation component 223 maydetermine that an unused resource is classified as an instance of asoftware application, a user account, or a storage volume. In anotherexample, multiple instances of a software application may exist withinthe distributed computing architecture, and the reclamation component223 classifies the instances based on the software version number of thesoftware application associated with each instance. The classificationcriteria may also include characteristics not directly related to thetype of resource, such as the date on which the resource was lastaccessed or the version number of a software application associated withthe resource.

The reclamation component 223 determines an expiration period for theresource based on one or more reclamation rules 229. For example, thereclamation rules 229 may indicate that a storage volume has anexpiration period of fifteen days, while an instance of a softwareapplication has an expiration period of thirty days. The reclamationrules 229 include any suitable rules for setting expiration periodsassociated with a reclaimable resource, as tailored for the distributedcomputing architecture 110.

The reclamation component 223 also is responsible for identifying acandidate owner of a reclaimable resource based on one or morecharacteristics of the resource. Examples of resource characteristicsinclude, without limitation, a username to which the resource isregistered, a username associated with one or more data files storedwithin the resource, and in cases where more than one candidate owner isidentified, the reclamation application may use any technically feasibletechnique for determining the most likely candidate owner. Thereclamation component 223 then notifies the candidate owner that theresource will be reclaimed at the termination of the expiration period.For example, the reclamation component 223 may send an email to thecandidate owner via network interface 215. The notification includesinformation identifying the resource and the expiration period for theresource based on the reclamation rules 229.

In certain circumstances, the reclamation component 223 may be unable todetermine candidate owner for an unused resource. For example, aresource may have no identifiable characteristics to identify acandidate owner. In another example, the reclamation component 223 mayhave determined a candidate owner and sent the candidate owner anotification, but the candidate owner is not the actual owner. Inanother example, the reclamation component 223 may have determined acandidate owner who no longer owns the resource. In such cases, thereclamation component 223 notifies the system administrator that nocandidate owner has been identified, and terminates the reclamation ofthe resource. The system administrator may then manually attempt toreclaim the resource.

Once the reclamation component 223 has notified the candidate owner, thecandidate owner may respond and claim the resource within the durationof the expiration period, otherwise the resource is reclaimed. Thecandidate owner may reclaim the resource through any technicallyfeasible means, such as replying to the notification, by accessing aspecific uniform resource locator (URL) associated with a website thatis configured to claim resources, or by requesting an extension to theexpiration period. If the candidate owner claims the resource, then thereclamation component 223 terminates the process for reclaiming theresource. Alternatively, the candidate owner may respond and requestthat the expiration period be extended. If the expiration period isextended, then the resource is still eligible for reclaiming, but thereclamation component 223 delays reclaiming the resource until theexpiration of the extended period. If the candidate owner does notrespond to the notification within the expiration period, then thereclamation component 223 proceeds to reclaim the resource.

FIG. 3 sets forth a flow diagram of method steps for reclaiming unusedresources within a distributed computing architecture 110, according toone embodiment of the present invention. Although the method steps aredescribed in conjunction with the systems of FIGS. 1-2, persons skilledin the art will understand that any system configured to perform themethod steps, in any order, is within the scope of the presentinvention.

As shown, a method 300 begins at step 302, where the reclamationcomponent 223 identifies an unused resource. For example, thereclamation component 223 may systematically scan a set of resources anddetermine that a resource is considered unused if the resource has notbeen accessed for the previous thirty days. At step 304, the reclamationcomponent 223 classifies the unused resource. For example, thereclamation component 223 may determine that the unused resource is anunused storage volume. At step 306, the reclamation component 223determines the expiration period for the resource according to apre-determined rule. For example, the reclamation component 223 maydetermine that a storage volume expiration period is fifteen days. Atstep 308, the reclamation component 223 attempts to identify thecandidate owner based on one or more characteristics of the resource.For example, the reclamation component 223 may examine the resource tosee whether the resource is registered to a particular user, whetherthere is a record of the user who last accessed the resource, the timewhen the resource was most recently accessed, or whether the resource isassociated with a particular user's account.

At step 310, the reclamation component 223 determines whether acandidate user has been identified. If a candidate user has not beenidentified, then the method 300 proceeds to step 312, where thereclamation component 223 alerts the system administer. The method 300then terminates.

If, however, in step 310, a candidate user has been identified, then themethod 300 proceeds to step 314, where the monitoring applicationnotifies the candidate owner via a generated email message, a systemmessage, or any other technically feasible means. At step 316, thereclamation component 223 determines whether a request to extend theexpiration period has been received and granted, such as by request ofthe candidate owner. If an extension of the expiration period has beengranted, then the method 300 proceeds to step 318, where the reclamationcomponent 223 where the reclamation component 223 extends the expirationperiod. The method 300 then proceeds to step 320, where the reclamationcomponent 223 waits for the duration of the extended expiration period.At step 322, the reclamation component 223 determines whether thecandidate owner has claimed the resource. If the candidate owner hasclaimed the resource, then the method 300 terminates.

If, however, in step 322, the candidate owner has not claimed theresource, then the method 300 proceeds to step 324, where thereclamation component 223 reclaims the resource. The method 300 thenterminates.

Returning to step 316, if an extension of the expiration period has notbeen granted, then the method proceeds to step 320 and continues asdescribed above.

In sum, a reclamation component 223 within a reclamation application 164searches a distributed computing architecture 110 for unused resourcessuch as storage volumes and out of date software applications. Aresource may be considered unused if, for example, the resource has notbeen accessed for an extended period. The resource is classified via oneor more classification criteria such as whether the resource is astorage volume. The reclamation component 223 determines an expirationperiod for the resource based on a set of reclamation rules 229. Thereclamation component 223 identifies a candidate owner based on one ormore characteristics of the resource, such as registration of theresource to or access of the resource by a particular username. Thereclamation component 223 notifies the candidate owner that the unusedresource is to be reclaimed at the termination of the expiration periodunless the candidate owner claims the resource. If the candidate ownerclaims the resource, then the reclamation component 223 terminates thereclamation of the resource. Alternatively, the candidate owner mayrequest an extension to the termination period before the resource isclaimed. If the candidate owner has not claimed the resource by the endof the expiration period, then the reclamation component 223 reclaimsthe resource. The resource may then be relinquished or redeployed by thesystem administrator.

Advantageously, unused resources within a distributed computingarchitecture 110 are reclaimed and subsequently relinquished orredeployed. Resources may be redeployed for other purposes, thusincreasing overall efficiency and utilization. Resources that are nolonger needed may be relinquished resulting in lower operating andmaintenance costs. Further, some unused resources may pose a securityrisk. Reclaiming such resources may improve security within thedistributed computing architecture 110.

While the foregoing is directed to embodiments of the present invention,other and further embodiments of the invention may be devised withoutdeparting from the basic scope thereof. For example, aspects of thepresent invention may be implemented in hardware or software or in acombination of hardware and software. One embodiment of the inventionmay be implemented as a program product for use with a computer system.The program(s) of the program product define functions of theembodiments (including the methods described herein) and can becontained on a variety of computer-readable storage media. Illustrativecomputer-readable storage media include, but are not limited to: (i)non-writable storage media (e.g., read-only memory devices within acomputer such as CD-ROM disks readable by a CD-ROM drive, flash memory,ROM chips or any type of solid-state non-volatile semiconductor memory)on which information is permanently stored; and (ii) writable storagemedia (e.g., floppy disks within a diskette drive or hard-disk drive orany type of solid-state random-access semiconductor memory) on whichalterable information is stored. Such computer-readable storage media,when carrying computer-readable instructions that direct the functionsof the present invention, are embodiments of the present invention.

Therefore, the scope of the present invention is determined by theclaims that follow.

What is claimed is:
 1. A computer-implemented method, comprising:generating a notification that a resource within a distributed computingenvironment is to be reclaimed when an expiration period ends; and ifthe resource is claimed before the expiration period ends, then notperforming an operation to reclaim the resource; or if the resource isnot claimed before the expiration period ends, then performing anoperation to reclaim the resource.
 2. The method of claim 1, wherein theresource has a classification, and a reclamation rule specifies a fixedexpiration period for the classification.
 3. The method of claim 1,further comprising identifying a candidate owner for the resource basedon a user name.
 4. The method of claim 1, further comprising determiningthat the resource can be reclaimed based on a date on which the resourcewas last accessed.
 5. The method of claim 1, wherein the resourcecomprises an instance of a software application, and further comprisingdetermining that the resource can be reclaimed based on a softwareversion number associated with the resource.
 6. The method of claim 1,further comprising receiving a request to extend the expiration period,and, in response to the request, extending the expiration period.
 7. Themethod of claim 1, wherein the resource comprises an instance of asoftware application, a user account, or a storage volume.
 8. Anon-transitory computer-readable storage medium including instructionsthat, when executed by a processor, cause the processor to perform thesteps of: generating a notification that a resource within a distributedcomputing environment is to be reclaimed when an expiration period ends;and if the resource is claimed before the expiration period ends, thennot performing an operation to reclaim the resource; or if the resourceis not claimed before the expiration period ends, then performing anoperation to reclaim the resource.
 9. The non-transitorycomputer-readable storage medium of claim 8, wherein the resource has aclassification, and a reclamation rule specifies a fixed expirationperiod for the classification.
 10. The non-transitory computer-readablestorage medium of claim 8, further comprising identifying a candidateowner for the resource based on a user name.
 11. The non-transitorycomputer-readable storage medium of claim 8, further comprisingdetermining that the resource can be reclaimed based on a date on whichthe resource was last accessed.
 12. The non-transitory computer-readablestorage medium of claim 8, wherein the resource comprises an instance ofa software application, and further comprising determining that theresource can be reclaimed based on a software version number associatedwith the resource.
 13. The non-transitory computer-readable storagemedium of claim 8, further comprising receiving a request to extend theexpiration period, and, in response to the request, extending theexpiration period.
 14. The non-transitory computer-readable storagemedium of claim 8, wherein the resource comprises an instance of asoftware application, a user account, or a storage volume.
 15. A system,comprising: a processor; and a memory coupled to the processor andincluding instructions that, when executed by the processor, cause theprocessor to: generate a notification that a resource within adistributed computing environment is to be reclaimed when an expirationperiod ends; and if the resource is claimed before the expiration periodends, then not perform an operation to reclaim the resource; or if theresource is not claimed before the expiration period ends, then performan operation to reclaim the resource.
 16. The system of claim 15,wherein the resource has a classification, and a reclamation rulespecifies a fixed expiration period for the classification.
 17. Thesystem of claim 15, further comprising identifying a candidate owner forthe resource based on a user name.
 18. The system of claim 15, furthercomprising determining that the resource can be reclaimed based on adate on which the resource was last accessed.
 19. The system of claim15, wherein the resource comprises an instance of a softwareapplication, and further comprising determining that the resource can bereclaimed based on a software version number associated with theresource.
 20. The system of claim 15, further comprising receiving arequest to extend the expiration period, and, in response to therequest, extending the expiration period.
 21. The system of claim 15,wherein the resource comprises an instance of a software application, auser account, or a storage volume.